dev/core#681 - Fatal Error on submitting "Change Case Status" activit… #13497
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(Standard links)
|
|
I've tested this and can confirm the issue on master, that this fixes it and that it is ok to merge |
|
This seems like a regression - should there be a 5.10.2 release for it? or will it have to wait for 5.11. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…y form
Overview
Before
From Console
After
works fine.
Technical Details
The updated datepicker submits the value as
yyyy-mm-dd hh:mm:sswhich is not validated as timestamp when fed to an sql query.Comments
Seems to be due to the recent datepicker updates made in the activity form.